Update post emitter script#47525
Merged
dargilco merged 9 commits intoJun 16, 2026
Merged
Conversation
howieleung
approved these changes
Jun 16, 2026
d20c8c4
into
feature/azure-ai-projects/2.3.0
4 of 9 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Emit from TypeSpec that uses the new "exact" client renames. This means we can remove all the simple variable or enum value renames. Also convert the post emitter script to a PowerShell file, since this is what the SDK generation pipeline will now run.
Update the PowerShell script to also include the remaining fix to emitted code I was previously doing manually. With this addition, we no longer need to apply any manual fixes. I already communicated this emitted code bug to the Python emitter team.